Apparatus and methods using invalidity indicators for buffered memory

ABSTRACT

A storage system includes a storage medium configured to store data and a buffer memory configured to buffer data to be written to the storage medium. The storage system further includes a controller configured to selectively transfer the buffered data to the storage medium responsive to an invalidity indicator received from an external source. For example, the invalidity indicator may comprise unwrite information received from an external source, e.g., information that indicates that selected buffered data corresponds to deleted file data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of application Ser. No. 11/230,994, filed Sep. 20, 2005, now U.S. Pat. No. 7,802,054, which claims the benefit of Korean Patent Application No. 2004-109826, filed Dec. 21, 2004 and hereby incorporated by reference herein in their entirety.

BACKGROUND OF THE INVENTION

The present invention relates to computing systems and methods and, more particularly, to computing systems including a storage system with buffer memory.

FIG. 1 is a block diagram illustrating a generic computing system. The computing system includes a host 10, e.g., a host computer system, and storage 20. The host 10 includes a central processing unit (not shown) and a main memory (not shown). The storage 20 is connected to the host 10 using a standardized interface, such as a small computer system interconnect (SCSI) interface, an enhanced small device interface (ESDI), or an intelligent drive electronic (IDE) interface. The storage 20 includes a storage medium 22, such as a hard disk or a floppy disk, a buffer memory 24 and a controller 26. The controller 26 is connected to the storage medium 22 and the buffer memory using conventional interfaces. The buffer memory 24 includes memory, such as a static random access memory SRAM or a dynamic random access memory DRAM. The buffer memory 24 is used for improving a write performance of the storage 20.

FIG. 2 is a view showing exemplary file processing for the computing system shown in FIG. 1. When an application program is executed at a high level, such as at the host 10, the application program generates files and the generated files are managed by a file system such as a file allocation table (FAT) file system. If the application program writes data in the generated files, the written data is transmitted to lower level, such as the storage 20, under control of the central processing unit. The transmitted data is temporally stored in the buffer memory of the storage 20. When the host 10 requests a file, data of the requested file is directly transferred from the storage 20 to the main memory of the host 10 or the data of the requested file is transferred to the main memory of the host 10 through the buffer memory 24. Data transferred through the buffer memory 24 may be temporally stored in the buffer memory 24.

Because the capacity of the buffer memory 24 usually is small in comparison to the capacity of the storage medium 22, it typically is not possible to store all of data transferred from the main memory to the storage medium 22 in the buffer memory 24. Therefore, the data stored in the buffer memory 24 is intermittently transferred to the storage medium 22 under control of the controller 26. The transfer of data from the buffer memory 24 to the storage medium 22 typically is automatically performed without intervention of the host 10. For example, the data temporally stored in the buffer memory 24 may be automatically transferred to the storage medium 22 if the buffer memory 24 lacks room for storing new data when the host 10 requests to perform a write operation, or if the storage 20 is in an idle state wherein no requests are received from the host 10 within a predetermined time period.

The above-mentioned computing system may have disadvantages. When data of a file processed by an application program of the host 10 is deleted, the data is treated as the deleted file by the file system at the host 10. Even if the data is considered deleted at the level of the host 10, the data may actually still be stored in the buffer memory 24. The data stored in the buffer memory 24 may then be automatically transferred to the storage medium 22 without intervention of the host 10 when the buffer memory 24 lacks room for storing new data. Although the data stored in the buffer memory becomes invalid because of the deletion at the high level, the invalid data may be unnecessarily written in the storage medium 22 because the controller 26 typically cannot determine the validity of data stored in the buffer memory 24. Accordingly, write performance of the storage 20 may be degraded, and a life time of the storage 20 may be shortened due to the unnecessary write operations. In addition, power may be wasted by unnecessary write operations.

SUMMARY OF THE INVENTION

In some embodiments of the present invention, a storage system includes a storage medium configured to store data and a buffer memory configured to buffer data to be written to the storage medium. The storage system further includes a controller configured to selectively transfer the buffered data to the storage medium responsive to an invalidity indicator received from an external source. For example, the invalidity indicator may include unwrite information received from an external source, e.g., information that indicates that selected buffered data corresponds to deleted file data.

In further embodiments, the controller is configured to invalidate selected buffered data responsive to the invalidity indicator. In particular, the controller may be configured to store write state information indicative of invalidity of the invalidated buffered data responsive to the invalidity indicator, and to prevent transfer of the invalidated buffered data from the buffer memory to the storage medium responsive to the stored write state information.

In additional embodiments of the present invention, the controller is configured to trigger a transcribe operation responsive to a storage limitation in the buffer memory and/or an idle state of the storage medium. The transcribe operation includes transferring valid buffered data from the buffer memory to the storage medium controller while foregoing transfer of the invalidated buffered data from the buffer memory to the storage medium. According to further embodiments, the controller may be further configured to enable reuse of storage space in the buffer memory occupied by the invalidated buffered data responsive to the invalidation of the invalidated buffered data.

In certain embodiments of the present invention, a computing system includes a storage system including a storage medium configured to store data, a buffer memory configured to buffer data to be written to the storage medium and a controller configured to selectively transfer the buffered data to the storage medium responsive to an invalidity indicator. The computing system further includes a host configured to transfer the data to the buffer memory and to provide the invalidity indicator to the storage system responsive to a data modification operation at the host. The invalidity indicator may include, for example, an unwrite command generated responsive to deletion of file data at the host.

In further embodiments of the present invention, methods are provided for operating a storage system including a storage medium and a buffer memory configured to store data to be written to the storage medium. A invalidity indicator related to data stored in the buffer memory is received from an external source, such as a computer host. Data stored in the buffer memory is selectively transferred to the storage medium responsive to the received invalidity indicator.

According to some embodiments of the present invention, a system for controlling data storage in a storage medium includes a buffer memory configured to buffer data to be written to the storage medium, and a controller configured to selectively transfer the buffered data to the storage medium responsive to an invalidity indicator received from an external source.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 is a block diagram illustrating a conventional computer system;

FIG. 2 illustrates conventional file processing operations of the computing system shown in FIG. 1;

FIG. 3 is a block diagram illustrating a computing system including a storage system in accordance with some embodiments of the present invention;

FIGS. 4A and 4B are diagrams showing a mapping table of a storage system in accordance with further embodiments of the present invention;

FIG. 5 is a flowchart illustrating exemplary operations for managing data stored in a storage system of a computing system in accordance with additional embodiments of the present invention; and

FIGS. 6A-6C are mapping diagrams illustrating exemplary write operations based on invalidity information for data stored in a buffer memory in a storage system of a computing system in accordance with still further embodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Specific exemplary embodiments of the invention now will be described with reference to the accompanying drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the drawings, like numbers refer to like elements. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “includes,” “including” and/or “including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present specification and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

It will be understood that although the terms first and second are used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. Thus a first item could be termed a second item, and similarly, a second item may be termed a first item without departing from the teachings of the present invention. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. The symbol “/” may also used as a shorthand notation for “and/or”.

In the present invention, an “unwrite,” “erase” or “delete” command, request or information represents a command or other information input to a storage system to invalidate data stored in a buffer memory and prevent its transfer from the buffer memory to a storage medium. A transfer of data from a buffer memory to a storage medium may be referred to as a “transcribe” or “flushing” operation.

FIG. 3 is a block diagram illustrating a computing system 1000 in accordance with some embodiments of the present invention. The computing system 1000 includes a host system 100 and a storage system 200. The storage system 200 may include, for example, a storage device coupled to the host system 100 using a standardized interface, such as a SCSI, ESDI, or IDE interface. It will be appreciated that other types of interfaces, including nonstandard interfaces, may be used to couple the host system 100 and the storage system 200. The storage system 200 may include memory integrated with the host system 100.

The host system 100 includes a central processing unit (CPU) 110 and a memory 120. The memory 120 may include a main memory of the host system 100. An application program 121 and a file system 122 are embodied in the memory 120. The file system 122 may include one or more file systems having a file allocation table (FAT) or other file system.

The host system 100 outputs an unwrite command to the storage system 200 when all or some of the data of a file processed by the application program 121 is to be deleted. The host system 100 may, for example, transmit the unwrite command accompanied by information relating to an address and/or size of the data to be deleted to the storage system 200.

A FAT file system, such as that shown in FIG. 2, may include a master boot record (MBR), a partition boot record (PBR), first and second file allocation tables (primary FAT, copy FAT) and a root directory. The data stored or to be stored in the storage system 200 can, for example, be identified using two items of information, such as a file name including the data and a path of a directory tree for reaching a place where the file is stored. Each entry of a directory stores information, such as a length of file (e.g. 32 bytes long), a file name, an extension name, a file property byte, a last modification date and time, a file size and a connection of a start-up cluster.

A predetermined character may be used as a first character of a file name to indicate a deleted file. For example, a hexadecimal number byte code E5h may be assigned to the first character of the file name for a deleted file to serve as a tag for indicating that the file is deleted. When a file is deleted, the CPU 110 may assign a predetermined character as the first character of the file name of the deleted file and also Output an unwrite command and/or other invalidity information corresponding to the deleted file to the storage system 200.

Still referring to FIG. 3, the storage system 200 includes a storage medium 220, a buffer memory 240 and a controller 260. The storage system 200 prevents writing of data stored in the buffer memory 240 to the storage medium 220 when the data of a file is considered deleted at a higher level of the storage system 200 and an invalidity indicator has been input to the storage system 200. The invalidity indicator may include the unwrite command, along with information about an address and a size of the deleted data.

The storage medium 220 may store all types of data, such as text, images, music and programs. The storage medium 220 may be a nonvolatile memory, such as a magnetic disk or a flash memory. However, it will be understood that the storage medium 220 is not limited to nonvolatile memory.

The buffer memory 240 is used to buffer data transfer between the host system 100 and storage medium 220. The buffer memory 240 may include high speed volatile memory, such as dynamic random access memory (DRAM) or static random access memory (SRAM), and/or nonvolatile memory, such as magnetoresistive random access memory (MRAM), parameter random access memory (PRAM), ferroelectric random access memory (FRAM), NAND flash memory or NOR flash memory.

The buffer memory 240 serves as a write buffer. For example, the buffer memory 240 may temporarily store data to be written in the storage medium 220 responsive to a request of the host system 100. The write buffer function of the buffer memory 240 can be selectively used. Occasionally, in a “write bypass” operation, data transferred from the host system may be directly transferred to the storage medium 220 without being stored in the buffet memory 240. The buffer memory 240 may also work as a read buffer. For example, the buffer memory 240 may temporarily store data read from the storage medium 220. Although FIG. 3 shows only one buffer memory, two or more buffer memories can be provided. In such embodiments, each buffer memory may be used exclusively as a write buffer or read buffer, or may serve as a write and read buffer.

The controller 260 controls the storage medium 220 and the buffer memory 240. When a read command is input from the host system 100, the controller 260 controls the storage medium 220 to cause transfer of data stored in the storage medium 220 directly to the host system 100 or to cause transfer of data stored in the storage medium 220 to the host system 100 via the buffer memory 240. When a write command is input from the host system 100, the controller 260 temporarily stores data related to the write command in the buffer memory 240. All or part of the data stored in the buffer memory 240 is transferred to the storage medium 220 when the buffer memory 240 lacks room for storing additional data or when the storage system 200 is idle. The storage system 200 may be considered idle when no requests have been received from the host system 100 within a predetermined time.

The controller 260 holds address mapping information for the storage medium 220 and the buffer memory 240 and a mapping table 261 for storing write state information representing validity/invalidity of stored data. The write state information is updated by invalidity information (e.g., an indicator) provided from an external device. The controller 260 controls the storage medium 220 and the buffer memory 240 to write all or part of data stored in the buffer memory 240 to the storage medium 220 based on the write state information in the mapping table 261. In some embodiments of the present invention, the storage medium 220 and the buffer memory 240 may be embodied using a flash memory.

As described above, the storage system 200 of the illustrated embodiments of the present invention determines whether or not to transfer all or part of data stored in the buffer memory 240 to the storage medium 220 by referring to the write state information. That is, the storage system 200 of the present invention receives the unwrite or other information representing that data stored in the buffer memory is invalid data from an external source device, such as the host system 100. In response to the unwrite or other invalidity indicator, the storage system 200 prevents writing of invalid data to the storage medium 220 from the buffer memory 240. In other words, the storage system 200 assigns a tag representing invalidity of data stored in the buffer memory 240 and selectively transfers data stored in the buffer memory 240 to the storage medium 220 based on the assigned tag. Accordingly, a write performance of the storage system 200 may be improved, which can reduce shortening of the life time of the storage system 200 caused by unnecessary write operations. Furthermore, power consumed by unnecessary write operations may be reduced.

FIGS. 4A and 4B are diagrams showing exemplary mapping tables which may be used by the controller 260 of FIG. 3 according to some embodiments of the present invention. In FIGS. 4A and 4B, “BBN” represents a block number of the buffer memory 240, “DCN” represents a cluster number of the storage medium 220, and “WSI” represents the write state information indicating whether the data stored in the buffer memory 240 is a valid or invalid. In the illustrated embodiments, it is assumed that the block size of the buffer memory 240 is identical to a size of a cluster having a plurality of sectors. However, the storage medium 220 need not be limited to this assumption. For example, an allocation unit of the storage medium 220 can correspond to a sector of a magnetic disc, or a page, sector or block of flash memory. In the FIGS. 4A and 4B, invalid data is indicated by an “X” and valid data is indicated by a “V”.

In FIG. 4A, it is also assumed that data sets FILE1, FILE2, FILE3 corresponding to three files is stored in the buffer memory 240 as valid data. The data sets FILE1, FILE2, FILE3 may not be stored in the storage medium 220 yet. The stored file data sets FILE1, FILE2, FILE3 are transferred to the storage medium 220 when the buffer memory 240 lacks room for storing new data or when the storage medium 220 becomes idle, as described above. The controller 260 updates the write state information of the file data sets FILE1, FILE2, FILE3 stored in the buffer memory 240 according to invalidity information transferred from the host system 100. For example, the file data set FILE2 is deleted in the host system 100 and the host system 100 transmits invalidity information for the file data set FILE2 to the controller 260, the invalidity information indicating that the file data set FILE2 has been deleted at the host system 100. When the controller 260 receives the invalidity information for the file data set FILE2, the controller 260 changes the write state information WSI of the file data set FILE2 to “X” to indicate that the file data set FILE2 is invalid.

FIG. 5 is a flowchart illustrating exemplary operations for managing data stored in a storage system in a computing system in accordance with some embodiments of the present invention. As mentioned above, a storage system 200 shown in FIG. 2 includes the storage medium 220 for storing data and the buffer memory 240 for temporally storing data to be written to the storage medium 220. As shown in FIG. 5, in a step S100, it is determined whether unwrite or other invalidity information is provided to the storage system 200. In a step S200, all or part of the corresponding data temporarily stored in the buffer memory 240 is marked invalid in response to the unwrite or other invalidity information. After invalidation, the invalid data is not written to the storage medium 220.

FIGS. 6A-6C are diagrams illustrating exemplary data management operations in accordance with further embodiments of the present invention. As described above with reference to FIG. 2, the controller 260 of the storage system 200 transfers data stored in the buffer memory 240 to the storage medium 220 by referring to the mapping table 261. Referring to FIG. 6A, it is assumed that there are three file data sets FILE1, FILE2, FILE3 stored in the buffer memory 240 as valid data. The controller 260 of the storage system 200 determines which data stored the buffer memory 240 is invalid based on the write state information WSI in the mapping table 261 that corresponds to the stored file data sets FILE1, FILE2, FILE3. As shown in FIG. 6A, the controller 260 controls the buffer memory 240 and the storage medium 220 to transfer the file data sets FILE1, FILE2, FILE3 from the buffer memory 240 to corresponding locations in the storage medium 220, as all of the file data sets FILE1 to FILE3 are tagged as being valid by the mapping table 261.

If invalidity information including, for example, an unwrite command, address information for the invalid data file and size information for the invalid data file, is input to the controller 260 before the transfer of corresponding data to the storage medium 220, the controller 260 invalidates data related to the invalidity information. For example, as shown in FIG. 6B, if the invalid data corresponds to the file data set FILE2, the controller 260 updates the write state information WSI of the mapping table 261 related to the file data set FILE2 to indicate that the file data set FILE2 is invalid. The controller 260 may then determine which data stored in the buffer memory 240 is invalid based on the write state information WSI in the mapping table 261. As shown in FIG. 6B, the file data FILE1 and FILE3 are tagged as valid data and the file data FILE2 is tagged as invalid data in the mapping table 261. Accordingly, the controller 260 controls the buffer memory 240 and the storage medium 220 to transfer the file data sets FILE1 and FILE3 to corresponding locations of the storage medium 220, while foregoing transfer the file data FILE2 to a corresponding location of the storage medium 220. Space in the buffer memory 240 occupied by the invalid file data set FILE2 may be used for storing new data in a subsequent new write/read operation.

In another example shown in FIG. 6C, it is assumed that only one data file set FILE1 is stored in the buffer memory 240. If invalidity information is input to the controller 260 before transfer of the data file set FILE1 to the storage medium 220, the controller 260 invalidates the data file set FILE1. In particular, the controller 260 updates the write state information WSI of the mapping table 261 related to the file data set FILE1 to show that the file data set FILE1 is invalid. After the updating, the controller 260 may then determine whether the data stored in the buffer memory 240 is invalid by referring to the write state information WSI of the mapping table 261 related to the file data FILE1. As shown in FIG. 6C, the file data set FILE1 is not transferred to the storage medium 220 because of the “X” state of the write state information WSI. Accordingly, transfer of invalid data is prevented when the storage medium 220 is idle. The space of the buffer memory 240 occupied by the invalid data may be used to store new data in a subsequent write operation.

Although the invalid data is written in the storage medium 220, files related to the invalid data stored in the storage medium 220 are not influenced by the stored invalid data. Furthermore, the controller 260 may selectively transfer the invalid data to the storage medium 220. That is, although the data stored in the buffer memory 240 is invalidated by the unwrite command, the controller 260 may selectively transfer the invalid data to the storage medium 220.

The storage system 200 described above controls data transfer operations between the buffer memory 240 and the storage medium 220 by referring to the mapping table including the write state information representing whether the data stored in the buffer memory 240 is invalid or valid. As described above, the write state information of the data may be provided from a source external to the storage system 200. Also, the data may be new data read and modified by the external source. It will be appreciated that storage systems according to various embodiments of the present invention may be used not only in computing systems, but also in devices that store data on a hard disk or in a flash memory, such as a MP3 player or other portable electronic device. By reducing transfer of invalid from a buffer memory to a storage medium, write performance and/or lifetime of the storage system can be improved. In addition, power consumption associated with unnecessary write operations can be reduced.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. 

1. A memory storage system comprising: an interface; a buffer memory configured to store data received by the memory storage system via the interface; a nonvolatile memory; a mapping table storing a validity status of the data stored in the buffer memory; and a controller configured to automatically write the data from the buffer memory to the nonvolatile memory; wherein, in response to a first command received by the memory storage system via the interface, a validity status of a first data in the mapping table is changed to an invalid status effective to disable the automatic writing of the first data from the buffer memory to the nonvolatile memory.
 2. The memory storage system of claim 1, wherein the mapping table stores information correlating the first data to a physical address of the nonvolatile memory.
 3. The memory storage system of claim 2, wherein the mapping table stores information correlating the first data to an address of the buffer memory.
 4. The memory storage system of claim 1, wherein the controller is configured to automatically write data from the buffer memory to the nonvolatile memory when the memory storage system is idle.
 5. The memory storage system of claim 1, wherein the controller is configured to automatically write data from the buffer memory to the nonvolatile memory in response to an amount of data stored in the buffer memory.
 6. The memory storage system of claim 5, wherein the controller is configured to automatically write data from the buffer memory to the nonvolatile memory as a function of the existence of room to store additional data in the buffer memory.
 7. The memory storage system of claim 1, wherein the interface is a small computer system interface (SCSI).
 8. The memory storage system of claim 1, wherein the interface is an integrated drive electronics (IDE) interface.
 9. The memory storage system of claim 1, wherein the first command is an unwrite command.
 10. The memory storage system of claim 1, wherein the first data is file data and the first command is received without file data to be stored in the storage system.
 11. The memory storage system of claim 1, wherein the first command is accompanied by address information regarding the first data.
 12. The memory storage system of claim 11, wherein the first command is accompanied by size information regarding the first data.
 13. The memory storage system of claim 1, wherein the buffer memory comprises volatile memory.
 14. The memory storage system of claim 1, wherein the buffer memory comprises a second non-volatile memory.
 15. The memory storage system of claim 1, wherein the buffer memory comprises NAND flash memory.
 16. The memory storage system of claim 1, wherein the non-volatile memory comprises NAND flash memory.
 17. A computer system, comprising: an interface connectable to a memory storage system including a buffer memory, a nonvolatile memory and a controller configured to automatically update the nonvolatile memory by writing data of the buffer memory to the nonvolatile memory; a central processing unit (CPU) configured to cause an unwrite command to be sent to the memory storage system via the interface, the unwrite command effective to cause an invalidity status to be assigned to first data stored in the buffer memory to prevent the controller of the memory storage system from automatically updating the nonvolatile memory with a writing of the first data to the non-volatile memory.
 18. The computer system of claim 17, further comprising: a file allocation table including information where a data file is stored, wherein, in a delete operation of a first data file, the CPU modifies the file allocation table to indicate the first data file is deleted and causes the unwrite command to be sent to the memory storage system via the interface to cause an invalidity status to be assigned to data of the first data file stored in the memory storage system.
 19. The computer system of claim 18, wherein in the delete operation of the first data file, the CPU modifies the file allocation table to provide a predetermined character as part of a name of the first data file stored in the file allocation table.
 20. The computer system of claim 17, wherein the CPU is configured to cause address location information associated with the first data file to be sent to the storage system with the unwrite command.
 21. The computer system of claim 20, wherein the CPU is configured to cause data size information to be sent to the storage system with the unwrite command.
 22. The computer system of claim 17, wherein the interface is a small computer system interface (SCSI).
 23. The computer system of claim 17, wherein the interface is an integrated drive electronics (IDE) interface.
 24. A method of operating a memory storage system, the memory storage system comprising a buffer memory, a non-volatile memory and a controller configured to automatically update the non-volatile memory with data stored in the buffer memory, the method comprising: receiving, via an interface of the memory storage system, first data; storing the first data in the buffer memory of the memory storage system; receiving, via the interface of the memory storage system, a first command; in response to the first command, disabling an automatic update of the non-volatile memory with respect to the first data stored in the buffer memory.
 25. The method of claim 24, further comprising: in response to the first command, updating a mapping table to provide an invalidity status of the first data in the mapping table.
 26. The method of claim 25, further comprising: during an automatic update operation by the controller to automatically update the non-volatile memory with data stored in the buffer memory, updating the non-volatile memory with data of the buffer memory without an invalidity status in the mapping table, and not updating the non-volatile memory with data of the buffer memory having an invalidity status in the mapping table.
 27. The method of claim 25, further comprising: in the mapping table, storing physical addresses of the nonvolatile memory associated with the first data stored in the buffer memory.
 28. The method of claim 27, further comprising: in the mapping table, storing addresses of the location of the first data in the buffer memory.
 29. The method of claim 24, further comprising: automatically writing data from the buffer memory to the non-volatile memory when the storage system is idle.
 30. The method of claim 24, further comprising: automatically writing data from the buffer memory to the non-volatile memory in response to an amount of data stored in the buffer memory.
 31. The method of claim 24, further comprising: automatically writing data from the buffer memory to the non-volatile memory as a function of the existence of room to store additional data in the buffer memory.
 32. The method of claim 24, wherein the interface is a small computer system interface (SCSI).
 33. The method of claim 24, wherein the interface is an integrated drive electronics (IDE) interface.
 34. The method of claim 24, wherein the first command is an unwrite command.
 35. The method of claim 24, further comprising: receiving file data as the first data; and receiving the first command without receiving file data associated with the first command.
 36. The method of claim 35, wherein the file data is generated by an application program in a host system.
 37. The method of claim 24, further comprising: receiving the first command with address information regarding the first data.
 38. The method of claim 37, further comprising: receiving the first command with size information of the first data.
 39. The method of claim 24, wherein the buffer memory comprises volatile memory.
 40. The method of claim 24, wherein the buffer memory comprises a second non-volatile memory.
 41. The method of claim 24, wherein the buffer memory comprises NAND flash memory.
 42. The method of claim 24, wherein the non-volatile memory comprises NAND flash memory.
 43. A method of storing data in a memory storage system including a buffer memory, a non-volatile memory, and a controller configured to automatically update the non-volatile memory by writing data stored in the buffer memory to the non-volatile memory, the method comprising the following steps performed by a host system: sending an unwrite command to the memory storage system via an interface of the host system, the unwrite command effective to cause an invalidity status to be assigned to first data stored in the buffer memory to prevent the controller of the memory storage system from automatically updating the nonvolatile memory with a writing of the first data to the non-volatile memory.
 44. The method of claim 43, further comprising: deleting a first data file including modifying a file allocation table in the host system to indicate the first data file is deleted; and sending the unwrite command to the memory storage system via the interface to cause an invalidity status to be assigned to data of the first data file stored in the memory storage system.
 45. The method of claim 44, further comprising generating the first data file by an application program in the host.
 46. The method of claim 44, further comprising modifying the file allocation table to provide a predetermined character as part of a name of the first data file in the file allocation table.
 47. The method of claim 44, further comprising sending address location information associated with the first data file to the storage system with the unwrite command.
 48. The method of claim 47, further comprising sending data size information to the storage system with the unwrite command.
 49. The method of claim 43, wherein the interface is a small computer system interface (SCSI).
 50. The method of claim 43, wherein the interface is an integrated drive electronics (IDE) interface. 